Sets our main struct and passes it to the parent class.
Returns a new rsvg handle. Must be freed with [method@GObject.Object.unref]. This handle can be used to load an image.
Loads the SVG specified by @data. Note that this function creates an [class@Rsvg.Handle] without a base URL, and without any [flags@Rsvg.HandleFlags]. If you need these, use [ctor@Rsvg.Handle.new_from_stream_sync] instead by creating a [class@Gio.MemoryInputStream] from your data.
Loads the SVG specified by @file_name. Note that this function, like [ctor@Rsvg.Handle.new], does not specify any loading flags for the resulting handle. If you require the use of [flags@Rsvg.HandleFlags], use [ctor@Rsvg.Handle.new_from_gfile_sync].
Creates a new [class@Rsvg.Handle] for @file.
Creates a new [class@Rsvg.Handle] for @stream.
Creates a new [class@Rsvg.Handle] with flags @flags. After calling this function, you can feed the resulting handle with SVG data by using [method@Rsvg.Handle.read_stream_sync].
This is used after calling [method@Rsvg.Handle.write] to indicate that there is no more data to consume, and to start the actual parsing of the SVG document. The only reason to call this function is if you use use [method@Rsvg.Handle.write] to feed data into the @handle; if you use the other methods like [ctor@Rsvg.Handle.new_from_file] or [method@Rsvg.Handle.read_stream_sync], then you do not need to call this function.
Frees @handle.
Gets the base uri for this [class@Rsvg.Handle].
Get the SVG's size. Do not call from within the size_func callback, because an infinite loop will occur.
Get the size of a subelement of the SVG file. Do not call from within the size_func callback, because an infinite loop will occur.
Computes the ink rectangle and logical rectangle of a single SVG element.
Computes the ink rectangle and logical rectangle of an SVG element, or the whole SVG, as if the whole SVG were rendered to a specific viewport.
Get the main Gtk struct
In simple terms, queries the width, height, and viewBox attributes in an SVG document.
Converts an SVG document's intrinsic dimensions to pixels, and returns the result.
Returns the pixbuf loaded by @handle. The pixbuf returned will be reffed, so the caller of this function must assume that ref.
Creates a GdkPixbuf the same size as the entire SVG loaded into @handle, but only renders the sub-element that has the specified @id (and all its sub-sub-elements recursively). If @id is NULL, this function renders the whole SVG.
Get the position of a subelement of the SVG file. Do not call from within the size_func callback, because an infinite loop will occur.
the main Gtk struct as a void*
Checks whether the element @id exists in the SVG document.
Do not call this function. This is intended for librsvg's internal test suite only.
Reads @stream and writes the data from it to @handle.
Draws a loaded SVG handle to a Cairo context. Please try to use [method@Rsvg.Handle.render_document] instead, which allows you to pick the size at which the document will be rendered.
Renders a single SVG element in the same place as for a whole SVG document (a "subset" of the document). Please try to use [method@Rsvg.Handle.render_layer] instead, which allows you to pick the size at which the document with the layer will be rendered.
Renders the whole SVG document fitted to a viewport.
Renders a single SVG element to a given viewport.
Renders a single SVG element in the same place as for a whole SVG document.
Set the base URI for @handle from @file.
Set the base URI for this SVG.
Sets the DPI at which the @handle will be rendered. Common values are 75, 90, and 300 DPI.
Sets the DPI at which the @handle will be rendered. Common values are 75, 90, and 300 DPI.
Sets the sizing function for the @handle, which can be used to override the size that librsvg computes for SVG images. The @size_func is called from the following functions:
Sets a CSS stylesheet to use for an SVG document.
Loads the next @count bytes of the image. You can call this function multiple times until the whole document is consumed; then you must call [method@Rsvg.Handle.close] to actually parse the document.
This function does nothing.
Do not use this function. Create an [class@Rsvg.Handle] and call [method@Rsvg.Handle.set_dpi] on it instead.
Do not use this function. Create an [class@Rsvg.Handle] and call [method@Rsvg.Handle.set_dpi_x_y] on it instead.
the main Gtk struct
the main Gtk struct
Get the main Gtk struct
the main Gtk struct as a void*
Gets a D Object from the objects table of associations.
The notify signal is emitted on an object when one of its properties has been changed. Note that getting this signal doesn't guarantee that the value of the property has actually changed, it may also be emitted when the setter for the property is called to reinstate the previous value.
Find the #GParamSpec with the given name for an interface. Generally, the interface vtable passed in as @g_iface will be the default vtable from g_type_default_interface_ref(), or, if you know the interface has already been loaded, g_type_default_interface_peek().
Add a property to an interface; this is only useful for interfaces that are added to GObject-derived types. Adding a property to an interface forces all objects classes with that interface to have a compatible property. The compatible property could be a newly created #GParamSpec, but normally g_object_class_override_property() will be used so that the object class only needs to provide an implementation and inherits the property description, default value, bounds, and so forth from the interface property.
Lists the properties of an interface.Generally, the interface vtable passed in as @g_iface will be the default vtable from g_type_default_interface_ref(), or, if you know the interface has already been loaded, g_type_default_interface_peek().
Increases the reference count of the object by one and sets a callback to be called when all other references to the object are dropped, or when this is already the last reference to the object and another reference is established.
Adds a weak reference from weak_pointer to @object to indicate that the pointer located at @weak_pointer_location is only valid during the lifetime of @object. When the @object is finalized, @weak_pointer will be set to %NULL.
Creates a binding between @source_property on @source and @target_property on @target.
Complete version of g_object_bind_property().
Creates a binding between @source_property on @source and @target_property on @target, allowing you to set the transformation functions to be used by the binding.
This is a variant of g_object_get_data() which returns a 'duplicate' of the value. @dup_func defines the meaning of 'duplicate' in this context, it could e.g. take a reference on a ref-counted object.
This is a variant of g_object_get_qdata() which returns a 'duplicate' of the value. @dup_func defines the meaning of 'duplicate' in this context, it could e.g. take a reference on a ref-counted object.
This function is intended for #GObject implementations to re-enforce a floating[floating-ref] object reference. Doing this is seldom required: all #GInitiallyUnowneds are created with a floating reference which usually just needs to be sunken by calling g_object_ref_sink().
Increases the freeze count on @object. If the freeze count is non-zero, the emission of "notify" signals on @object is stopped. The signals are queued until the freeze count is decreased to zero. Duplicate notifications are squashed so that at most one #GObject::notify signal is emitted for each property modified while the object is frozen.
Gets a named field from the objects table of associations (see g_object_set_data()).
Gets a property of an object.
This function gets back user data pointers stored via g_object_set_qdata().
Gets properties of an object.
Gets @n_properties properties for an @object. Obtained properties will be set to @values. All properties must be valid. Warnings will be emitted and undefined behaviour may result if invalid properties are passed in.
Checks whether @object has a floating[floating-ref] reference.
Emits a "notify" signal for the property @property_name on @object.
Emits a "notify" signal for the property specified by @pspec on @object.
Increases the reference count of @object.
Increase the reference count of @object, and possibly remove the floating[floating-ref] reference, if @object has a floating reference.
Removes a reference added with g_object_add_toggle_ref(). The reference count of the object is decreased by one.
Removes a weak reference from @object that was previously added using g_object_add_weak_pointer(). The @weak_pointer_location has to match the one used with g_object_add_weak_pointer().
Compares the user data for the key @key on @object with @oldval, and if they are the same, replaces @oldval with @newval.
Compares the user data for the key @quark on @object with @oldval, and if they are the same, replaces @oldval with @newval.
Releases all references to other objects. This can be used to break reference cycles.
Each object carries around a table of associations from strings to pointers. This function lets you set an association.
Like g_object_set_data() except it adds notification for when the association is destroyed, either by setting it to a different value or when the object is destroyed.
Sets a property on an object.
This sets an opaque, named pointer on an object. The name is specified through a #GQuark (retrieved e.g. via g_quark_from_static_string()), and the pointer can be gotten back from the @object with g_object_get_qdata() until the @object is finalized. Setting a previously set user data pointer, overrides (frees) the old pointer set, using #NULL as pointer essentially removes the data stored.
This function works like g_object_set_qdata(), but in addition, a void (*destroy) (gpointer) function may be specified which is called with @data as argument when the @object is finalized, or the data is being overwritten by a call to g_object_set_qdata() with the same @quark.
Sets properties on an object.
Sets @n_properties properties for an @object. Properties to be set will be taken from @values. All properties must be valid. Warnings will be emitted and undefined behaviour may result if invalid properties are passed in.
Remove a specified datum from the object's data associations, without invoking the association's destroy handler.
This function gets back user data pointers stored via g_object_set_qdata() and removes the @data from object without invoking its destroy() function (if any was set). Usually, calling this function is only required to update user data pointers with a destroy notifier, for example: |[<!-- language="C" --> void object_add_to_user_list (GObject *object, const gchar *new_string) { // the quark, naming the object data GQuark quark_string_list = g_quark_from_static_string ("my-string-list"); // retrieve the old string list GList *list = g_object_steal_qdata (object, quark_string_list);
If @object is floating, sink it. Otherwise, do nothing.
Reverts the effect of a previous call to g_object_freeze_notify(). The freeze count is decreased on @object and when it reaches zero, queued "notify" signals are emitted.
Decreases the reference count of @object. When its reference count drops to 0, the object is finalized (i.e. its memory is freed).
This function essentially limits the life time of the @closure to the life time of the object. That is, when the object is finalized, the @closure is invalidated by calling g_closure_invalidate() on it, in order to prevent invocations of the closure with a finalized (nonexisting) object. Also, g_object_ref() and g_object_unref() are added as marshal guards to the @closure, to ensure that an extra reference count is held on @object during invocation of the @closure. Usually, this function will be called on closures that use this @object as closure data.
Adds a weak reference callback to an object. Weak references are used for notification when an object is disposed. They are called "weak references" because they allow you to safely hold a pointer to an object without calling g_object_ref() (g_object_ref() adds a strong reference, that is, forces the object to stay alive).
Removes a weak reference callback to an object.
Clears a reference to a #GObject.
[class@Rsvg.Handle] loads an SVG document into memory.
This is the main entry point into the librsvg library. An [class@Rsvg.Handle] is an object that represents SVG data in memory. Your program creates an [class@Rsvg.Handle] from an SVG file, or from a memory buffer that contains SVG data, or in the most general form, from a GInputStream that will provide SVG data.
Librsvg can load SVG images and render them to Cairo surfaces, using a mixture of SVG's [static mode] and [secure static mode]. Librsvg does not do animation nor scripting, and can load references to external data only in some situations; see below.
Librsvg supports reading SVG 1.1 data, and is gradually adding support for features in SVG 2. Librsvg also supports SVGZ files, which are just an SVG stream compressed with the GZIP algorithm.
[static mode]: https://www.w3.org/TR/SVG2/conform.html#static-mode [secure static mode]: https://www.w3.org/TR/SVG2/conform.html#secure-static-mode
The "base file" and resolving references to external files
When you load an SVG, librsvg needs to know the location of the "base file" for it. This is so that librsvg can determine the location of referenced entities. For example, say you have an SVG in /foo/bar/foo.svg and that it has an image element like this:
In this case, librsvg needs to know the location of the toplevel /foo/bar/foo.svg so that it can generate the appropriate reference to /foo/bar/resources/foo.png.
Security and locations of referenced files
When processing an SVG, librsvg will only load referenced files if they are in the same directory as the base file, or in a subdirectory of it. That is, if the base file is /foo/bar/baz.svg, then librsvg will only try to load referenced files (from SVG's <image> element, for example, or from content included through XML entities) if those files are in /foo/bar/<anything> or in /foo/bar/<anything>\/.../<anything>. This is so that malicious SVG files cannot include files that are in a directory above.
The full set of rules for deciding which URLs may be loaded is as follows; they are applied in order. A referenced URL will not be loaded as soon as one of these rules fails:
1. All data: URLs may be loaded. These are sometimes used to include raster image data, encoded as base-64, directly in an SVG file.
2. All other URL schemes in references require a base URL. For example, this means that if you load an SVG with [ctor@Rsvg.Handle.new_from_data] without calling [method@Rsvg.Handle.set_base_uri], then any referenced files will not be allowed (e.g. raster images to be loaded from other files will not work).
3. If referenced URLs are absolute, rather than relative, then they must have the same scheme as the base URL. For example, if the base URL has a file scheme, then all URL references inside the SVG must also have the file scheme, or be relative references which will be resolved against the base URL.
4. If referenced URLs have a resource scheme, that is, if they are included into your binary program with GLib's resource mechanism, they are allowed to be loaded (provided that the base URL is also a resource, per the previous rule).
5. Otherwise, non-file schemes are not allowed. For example, librsvg will not load http resources, to keep malicious SVG data from "phoning home".
6. A relative URL must resolve to the same directory as the base URL, or to one of its subdirectories. Librsvg will canonicalize filenames, by removing ".." path components and resolving symbolic links, to decide whether files meet these conditions.
Loading an SVG with GIO
This is the easiest and most resource-efficient way of loading SVG data into an [class@Rsvg.Handle].
If you have a GFile that stands for an SVG file, you can simply call [ctor@Rsvg.Handle.new_from_gfile_sync] to load an [class@Rsvg.Handle] from it.
Alternatively, if you have a GInputStream, you can use [ctor@Rsvg.Handle.new_from_stream_sync].
Both of those methods allow specifying a GCancellable, so the loading process can be cancelled from another thread.
Loading an SVG from memory
If you already have SVG data in a byte buffer in memory, you can create a memory input stream with [ctor@Gio.MemoryInputStream.new_from_data] and feed that to [ctor@Rsvg.Handle.new_from_stream_sync].
Note that in this case, it is important that you specify the base_file for the in-memory SVG data. Librsvg uses the base_file to resolve links to external content, like raster images.
Loading an SVG without GIO
You can load an [class@Rsvg.Handle] from a simple filename or URI with [ctor@Rsvg.Handle.new_from_file]. Note that this is a blocking operation; there is no way to cancel it if loading a remote URI takes a long time. Also, note that this method does not let you specify [flags@Rsvg.HandleFlags].
Otherwise, loading an SVG without GIO is not recommended, since librsvg will need to buffer your entire data internally before actually being able to parse it. The deprecated way of doing this is by creating a handle with [ctor@Rsvg.Handle.new] or [ctor@Rsvg.Handle.new_with_flags], and then using [method@Rsvg.Handle.write] and [method@Rsvg.Handle.close] to feed the handle with SVG data. Still, please try to use the GIO stream functions instead.
Resolution of the rendered image (dots per inch, or DPI)
SVG images can contain dimensions like "5cm" or "2pt" that must be converted from physical units into device units. To do this, librsvg needs to know the actual dots per inch (DPI) of your target device. You can call [method@Rsvg.Handle.set_dpi] or [method@Rsvg.Handle.set_dpi_x_y] on an [class@Rsvg.Handle] to set the DPI before rendering it.
Rendering
The preferred way to render a whole SVG document is to use [method@Rsvg.Handle.render_document]. Please see its documentation for details.
API ordering
Due to the way the librsvg API evolved over time, an [class@Rsvg.Handle] object is available for use as soon as it is constructed. However, not all of its methods can be called at any time. For example, an [class@Rsvg.Handle] just constructed with [ctor@Rsvg.Handle.new] is not loaded yet, and it does not make sense to call [method@Rsvg.Handle.render_document] on it just at that point.
The documentation for the available methods in [class@Rsvg.Handle] may mention that a particular method is only callable on a "fully loaded handle". This means either:
* The handle was loaded with [method@Rsvg.Handle.write] and [method@Rsvg.Handle.close], and those functions returned no errors.
* The handle was loaded with [method@Rsvg.Handle.read_stream_sync] and that function returned no errors.
Before librsvg 2.46, the library did not fully verify that a handle was in a fully loaded state for the methods that require it. To preserve compatibility with old code which inadvertently called the API without checking for errors, or which called some methods outside of the expected order, librsvg will just emit a g_critical() message in those cases.
New methods introduced in librsvg 2.46 and later will check for the correct ordering, and panic if they are called out of order. This will abort the program as if it had a failed assertion.